-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support relaunch debug protocol #181
Conversation
Co-authored-by: Bronley Plumb <[email protected]>
…Promise to isConnected
…adapter and when application is ready to launch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few changes requested, but looking great!
Co-authored-by: Bronley Plumb <[email protected]>
Co-authored-by: Bronley Plumb <[email protected]>
… it needs to be destroyed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this, everything seems to be working properly. Thanks!
Persist the debug session for debug protocol. This is accomplished by parsing the telnet logs for the line "Waiting for debugging connection" and then creating the control port. When the application is closed, we continue to parse the telnet logs for that line. When that line is detected the control port will be created again.
A new signal
app-ready
is emitted to letBrightScriptDebugSession
know the debug adapters are ready. Both adapters have to emit this signal.When the app is closed via a home key press, reset the breakpoint managers state for the debug protocol.